| | [ Return to Bugs & Features | Roadmap 1.1 | SVN ⇄ GIT ]
STR #1681
| Application: | FLTK Library |
|---|
| Status: | 1 - Closed w/Resolution |
|---|
| Priority: | 4 - High, e.g. key functionality not working |
|---|
| Scope: | 2 - Specific to an operating system |
|---|
| Subsystem: | WIN32 |
|---|
| Summary: | Window refresh issues |
|---|
| Version: | 1.1-current |
|---|
| Created By: | matt |
|---|
| Assigned To: | matt |
|---|
| Fix Version: | 1.1-current (SVN: v5836) |
|---|
| Update Notification: | |
|---|
Trouble Report Files:
No files
Trouble Report Comments:
| |
| #1 | matt
01:34 May 16, 2007 |
| When there is a high CPU load, FLTK may forget to refresh areas while another window is dragged across the FLTK window. | |
| |
| #2 | matt
05:48 May 16, 2007 |
| On WIN32 WM_PAINT messages, FLTK would first render the damaged area and then set the area as valid again. While this is mostly fine on single CPU machines, multi-CPU machines may re-invalidate areas that are currently drawn, resulting in unrendered strips when another window was moved quickly across an FLTK window during its redraw phase.
The new implementation validates the damaged area as quickly as possible, allowing new damage requests to be handled correctly, even while we are still redrawing the same damaged area. | |
[ Return to Bugs & Features ]
|
| |
